v1.16.0 Release Notes

Zadig v1.16.0 was released on December 30, 2022.

# Feature List

Project

• Added developer dashboard
• Project list supports search
• Helm services support creation from common code sources
• K8s YAML templates and K8s YAML project service variables enhancement

Workflow

• Workflow supports views
• Workflow supports multi-PR merge build
• Workflow supports Chinese names
• Workflow IM notifications support specifying users (Feishu & WeCom)
• Custom workflow code change trigger branch selection supports regular expressions
• Custom workflow supports code scanning
• Custom workflow supports image distribution tasks
• Custom workflow supports parameter passing between tasks
• Custom workflow supports shared storage between tasks
• Custom workflow adds pass rate and duration analysis data
• Custom workflow adds environment preparation stage
• Workflow list adds execution information

Code Scanning

• Code scanning supports custom build images
• Code scanning links support jumping to corresponding sonar projects

System

• Added internationalization (i18n) support
• Quick link entry optimization
• Build templates/Helm Chart templates add reference lists
• AWS object storage integration adds region configuration
• Image registry selection supports global search
• Package management version updates

Other Optimizations and Bug Fixes

• 32 experience and interaction detail optimizations
• Workflow/service logs support custom colors
• Workflow list style optimization
• Product workflow execution workflow task openAPI optimization
• Code branch selection component interaction optimization
• Test task execution does not perform image registry login operations
• K8s YAML project environment related error messages displayed in service list
• Fixed issue where workflow/test/code scanning cannot execute when names exceed certain length
• Fixed custom workflow cache path rendering $WORKSPACE variable issue
• Fixed issue where multi-line commit msg causes workflow execution failure
• Optimized frontend font reference loading, removed external font references, improved page loading speed

# Business Change Notice

The new version makes the following content adjustments. Corresponding features configured in older versions will not be affected after upgrade:

• Original Tencent Cloud EKS is no longer supported. Enterprise version supports Tencent Cloud TKE Serverless and has passed compatibility testing
• Cluster management - task scheduling (forced scheduling), Dind resource scheduling configuration are included in enterprise version scope
• Project - version management is included in enterprise version scope
• GitOps automatic updates or synchronization of service configuration/service variables are included in enterprise version scope

# Version Upgrade Process

# Database Backup

If already in production use, be sure to backup the database before upgrading

1. Database backup commands:

• Backup MongoDB data

mongodump -h IP --port PORT -u USERNAME -p PASSWORD -d DATABASE -o FILE_PATH

• Backup MySQL data

mysqldump -h <HOST> -P <PORT> -u root -p user > user.sql
mysqldump -h <HOST> -P <PORT> -u root -p dex > dex.sql

2. Database restore commands:

• Restore MongoDB data

mongorestore -h IP --port PORT -u USERNAME -p PASSWORD -d DATABASE --drop FILE_PATH

• Restore MySQL data

# Execute the following in MySQL:
mysql> drop database user;
mysql> create database user;
mysql> drop database dex;
mysql> create database dex;
# Execute the following data recovery operations from command line:
mysql -h <HOST> -P <PORT> -u root -p user < user.sql
mysql -h <HOST> -P <PORT> -u root -p dex < dex.sql

# Upgrade Operations

Please execute corresponding upgrade steps according to different installation methods.

# Installation Method: All in One Installation Mode or Installation on Existing Kubernetes

For both installation methods, use scripts from Installation on Existing Kubernetes^New for upgrade.

# Installation Method: Helm Command Installation

For this installation method, execute the following steps to upgrade to v1.16.0:

1. Execute the following command and check the zadig.yaml file. If the file contains image information (i.e., tag:a.b.c), it needs to be manually deleted.

helm get values <Release Name> -n <Zadig Namespace>  > zadig.yaml

2. Execute upgrade command according to installation method.

• Domain method:

export NAMESPACE=<Zadig Installation NAMESPACE>

helm repo update
helm upgrade -f zadig.yaml <release_name> koderover-chart/zadig --namespace ${NAMESPACE} --version=1.16.0

• IP + PORT method:

export NAMESPACE=<Zadig Installation NAMESPACE>
export PORT=<Any port between 30000-32767, different from initially used port>

helm repo update
helm upgrade -f zadig.yaml <release_name> koderover-chart/zadig --namespace ${NAMESPACE} \
    --set gloo.gatewayProxies.gatewayProxy.service.httpNodePort=${PORT} \
    --set gloo.gatewayProxies.gatewayProxy.service.type=NodePort --version=1.16.0